#2280 expired some deprecations. Should that be noted in the deprecations section?

Maybe a note that we now officially support python 3.12?

Something about the whereabouts of the feature download script might be useful for those who need to use it (#2263).

Over in Iris, we have started including a reviewer credit for the more substantial changes (e.g. v3.8 features). What do you think about doing that here? I definitely think you deserve some credit for the GridLiner and FeatureArtist changes!

#2280 expired some deprecations. Should that be noted in the deprecations section?

Maybe a note that we now officially support python 3.12?

Something about the whereabouts of the feature download script might be useful for those who need to use it (#2263).

Thanks! I added all of these.

Over in Iris, we have started including a reviewer credit for the more substantial changes (e.g. v3.8 features). What do you think about doing that here? I definitely think you deserve some credit for the GridLiner and FeatureArtist changes!

That is nice, I think that'd be a great idea. It'd also be good if we start building this file as we go rather than having someone go through old commits and PRs to see what was changed :) I just asked questions during the review, you found the answers! Much less work for me, so I appreciate all the effort you put into updating those features.

I think this is good to go if no-one else has comments. @greglucas do you want to squash the commits? Feel free to self-merge either way.

I have set the release date for tomorrow April 4th in this change note now. That might be optimistic, but I think this PR and the numpy 2.0 build #2366 are the only two PRs needed before we can release, so if those go in I think we should release to prepare for Python 3.12+ and numpy 2.0+.

🤔 There is a lot of flakiness going on in the tests right now too. I had to rerun failed jobs a few times before they succeeded, and they are on image comparison tests without network requirements which seems odd to me.